@akien-mga Please don't merge yet.

I wanted to ask if using MAX(1.0, EDSCALE) instead of MAX(1.0f, EDSCALE) is intentional, for example here:
https://github.com/godotengine/godot/blob/88942a6637a9e460c715e3299758d4b85915aaac/editor/plugins/sprite_frames_editor_plugin.cpp#L1237-L1244
But now when I think of it, it probably doesn't really make a difference. 😄 And if it does, probably it's like this in way more places than just here.
So this should be fine to merge, sorry for stopping.

@kleonc Indeed that would make sense. EDSCALE returns a float, and these fields are float, so it's better to use it consistently rather than casting to double and back to float. I checked if there are other places around the engine to fix, this is the only file with the exact text MAX(1.0, EDSCALE), so I think it's worth making that change in this PR (make them MAX(1.0f, EDSCALE)).

EDIT: Except thumbnail_default_size is an integer, so that one should be MAX(1, EDSCALE)

@aaronfranke Ok, I've changed those.

Thanks!